Set Go garbage collection target percentage to 400% #5034
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dmitryax
force-pushed
the
set-gogc-to-400
branch
from
6c800d9 to
d3aba5d
Compare
After removal of memory_ballast extension in v0.97.0, the Go garbage collection is running more aggressively, which increased CPU usage and leads to reduced throughput of the collector. This change reduces the frequency of garbage collection cycles to improves performance of the collector for typical workloads. As a result, the collector will report higher memory usage, but it will be bound to the same configured limits. If you want to revert to the previous behavior, set the `GOGC` environment variable to `100`.
dmitryax
force-pushed
the
set-gogc-to-400
branch
from
d3aba5d to
94159d3
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After the removal of the memory_ballast extension in v0.97.0, the Go garbage collection is running more aggressively, which increases CPU usage and leads to reduced throughput of the collector. This change reduces the frequency of garbage collection cycles to improve the collector's performance for typical workloads. As a result, the collector will report higher memory usage, but it will be bound to the same configured limits. If you want to revert to the previous behavior, set the
GOGCenvironment variable to100.